Installation Kyocera Control Messenger

• MandatorGuid: Client GUID when operating in a client environment (otherwise empty).
• MultipleInstances: Specifies whether multiple instances of the Messenger should be started on one computer. By default only one instance may be started (false). Several may only be started for test purposes (true).
• WebClientUrl: Enter the URL for the call of the WebClient here - the WebClient can be called via the Messenger context menu. If this URL is not set, the menu item Open WebClient is grayed out.
• DontUseNlogMongo: With this setting you can prevent (true) or not prevent (false) logs being written to MongoDB - the logs should only be written to MongoDB for debugging purposes (default true).

• SkipDefaultPrinter: If Messenger is used to connect printer queues, it is possible to specify whether the user's default printer should be kept (true) or not (false).
• KeepExistingPrinters: If Messenger is used to connect printer queues, it is possible to specify whether all of the user’s printers that are already connected should be kept (true), or whether all existing printer queues should be removed (false).

• MqttPortList: Messenger communication ports with the NotificationService (standard 1883,1884).
• MqttNodeList: List of hostnames on which a NotificationService is running.
• MqttUserName: Technical user for technical communication (standard mqttsystem). This entry must match the entry in the LocalService.config of the NotificationService.
• MqttPassword: Password of the technical user for technical communication. This entry must match the entry in the LocalService.config of the NotificationService.
• MqttEncryptionKey: Key for transmission using encryption. This entry must match the entry in the LocalService.config of the NotificationService.

It is possible to set up Kyocera Control Messenger so that it is responsible for the transmission of print jobs (print proxy). This enables Messenger to forward the print job that has been initiated to a directly connected network printer in case the connection to the NotificationService is lost. The printer can be specified via the LocalService.config or via the installation query or can be stored in the WebAdmin for the client PC. See Direct printer

The following entries must be set in the LocalService.config of Messenger:

• ProxyRemoteHost: Hostname of the PrintService to which the print data are to be transferred.
• ProxyRemotePorts: Ports on which the print service receives the print jobs (incoming print), e.g. 49500,49501)
• ProxyLocalPorts: Local ports to be opened by the Messenger to accept a print job from a local printer driver (comma separated list). The first entry of the local port is forwarded on the first entry of the ProxyRemotePort, the second entry on the second entry, etc. (the number must match, e.g. 49500,49501).
• ProxyRemoteUrls: A print job received on one of the ports entered under ProxyLocalPorts can also be forwarded to the server via IPP or IPPS. For this purpose, a list of IPP URLs is specified at ProxyRemoteUrls (e.g. ipps://server/PrintService/ipp/Standard, ipps://server/PrintService/ipp/directprint). The number of entries must match the number in the ProxyLocalPorts list.
  IMPORTANT: If forwarding to remote URLs is required, the ProxyRemotePorts list must be empty.
• ProxyBackupHost: If the print job cannot be sent to the PrintService specified under ProxyRemoteHost, it is sent to the ProxyBackupHost (on the ProxyBackupPort or the ProxyBackupUrl).
• ProxyBackupPort: Port on which the print job is sent to the ProxyBackupHost.
• ProxyBackupUrl: URL to which the print job is sent if sending to the ProxyRemoteHost or ProxyRemoteUrl failed (e.g. ipps://backupserver/PrintService/ipp/Standard).
  IMPORTANT: If forwarding to backup URLs, the ProxyBackupPort must be empty.